so are editing actions done what about creation, deletion, duplication creation isnt editing and doesnt need to match anything, w store movement could come here too
creation needs ( data, numberOfCopies, additionalConfig) is tied to store currently creation is handled in memory, if one wants more they can call a duplication function, maybe a wrapper could be provided around this
duplication, needs ( filter, copies, additional config) is tied to a store
deletion needs ( filter)
movement needs ( filter, dest store, delete old query)
these all have in common that they manipulate the prescence of data and not the contents so they could all be managed under one function that manages prescence manipulation should they have similar parameters needed
I think the current creation mechanism is decent, when implementing duplication, we could just run the duplication after creation to create multiple copies
movement can be handled by the store, unless anything special is to be done, they can just read in the data and run the ltsd instanciation func for each one in the new store
since the parameters required are different these could be different functions that are grouped together in the 1d code text space
no i will group them to make future edits to the interface easier